You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using npm as my package manager of choice.
When I run commands like npm run dev or npm run build a new packageManager field with value pnpm is added to the package.json.
The packageManager shouldn't be guessed and it should be up to the user to add it to their package.json. Setting the value to npm@version will stop Plasmo interfering but this isn't something I'd want to include in my project until the field supports version ranges nodejs/corepack#95.
Uh oh!
There was an error while loading. Please reload this page.
What happened?
I'm using
npm
as my package manager of choice.When I run commands like
npm run dev
ornpm run build
a newpackageManager
field with valuepnpm
is added to thepackage.json
.The
packageManager
shouldn't be guessed and it should be up to the user to add it to theirpackage.json
. Setting the value tonpm@version
will stop Plasmo interfering but this isn't something I'd want to include in my project until the field supports version ranges nodejs/corepack#95.Version
Latest
What OS are you seeing the problem on?
Windows
(OPTIONAL) Contribution
Code of Conduct
The text was updated successfully, but these errors were encountered: